Embraer EMB-110 Bandeirante

Historical safety data and incident record for the Embraer EMB-110 Bandeirante aircraft.

Safety Rating

9.4/10

Total Incidents

78

Total Fatalities

476

Incident History

September 16, 2023 14 Fatalities

Sales Serviços Aéreos

Eldorado do Sul Rio Grande do Sul

The airplane departed Jundiaí on a cargo flight to Eldorado do Sul, carrying two pilots and a load of automotive parts. On final approach, the airplane crash landed in a rice paddy field and came to rest with its left wing detached. Both pilots were slightly injured.

Táxi Aéreo Ribeiro

Foz do Iguaçu Paraná

Shortly after takeoff from Foz do Iguaçu-Cataratas Airport, while climbing, the crew reported technical problems and elected to return. The crew realized he could not make it so he attempted an emergency landing in a corn field. Upon landing, the aircraft lost its undercarriage and slid for few dozen metres before coming to rest. Among the four occupants, one passenger was slightly injured and the aircraft was damaged beyond repair.

June 29, 2013 2 Fatalities

Batair Cargo

Francistown North-East District

The crew was performing a cargo flight from Lanseria to Lubumbashi with an intermediate stop at Francistown Airport to refuel, and the aircraft was carrying a load of ion exchange resins for water purification. During an early morning approach, the crew encountered poor visibility due to foggy conditions, abandoned the approach and initiated a go-around procedure. During a second approach from the opposite direction, the crew informed ATC he established a visual contact with the runway when the aircraft crashed in a bushy area located some 4,6 km short of runway.

Taxi Aéreo Weiss

Cascavel Paraná

The twin engine aircraft departed Sorocaba on a cargo flight to Cascavel, carrying two pilots and a load consisting of pharmaceutical materials. On final approach in low visibility due to bad weather conditions and night, the aircraft descended below the glide and impacted the ground 700 metres short of runway 33. On impact, it lost its undercarriage then slid for 150 metres before coming to rest. Both pilots escaped uninjured while the aircraft was damaged beyond repair. Visibility at the time of the accident was 1,200 metres with mist, local patches of fog and ceiling at 100 feet. Cascavel Airport was equipped with an NDB only.

January 25, 2010 2 Fatalities

Piquiatuba Taxi Aéreo

Senador José Porfírio Pará

Following an uneventful flight from Belém, the crew started the descent to Senador José Porfirio-Wilma Rebelo Airport in marginal weather conditions. On approach, the crew noticed an elevation of the left engine turbine temperature. The captain reduced the power on both engines and elected to make an emergency landing when the aircraft stalled and crashed in an open field located 4 km short of runway. The captain and a passenger were killed. All eight other occupants were killed, three seriously. The aircraft was destroyed.

February 7, 2009 24 Fatalities

Manaus Aerotáxi

Manacapuru Amazonas

The twin engine aircraft departed Coari Airport at 1240LT on a charter flight to Manaus-Eduardo Gomes Airport, carrying 26 passengers and two pilots. About 30 minutes into the flight, while cruising at FL115, the crew informed ATC that the left engine failed and elected to divert to the unused Manacapuru Airfield. While approaching runway 08, the aircraft rolled to the left to an angle of 30° then crashed in the Rio Manacapuru. 24 people were killed while 4 passengers were slightly injured.

Rico Linhas Aéreas - Rondonia Importaçao e Comercio

Coari Amazonas

The twin engine aircraft departed Manaus-Eduardo Gomes Airport on a flight to Carauari, carrying 15 passengers and two pilots. About 50 minutes into the flight, while cruising at an altitude of 8,500 feet, the right engine failed. The crew elected several times to restart it but without success. After the crew informed ATC about his situation, he was cleared to divert to Coari Airport located about 37 km from his position. Because the aircraft was overloaded and one engine was inoperative, the crew was approaching Coari Airport runway 28 with a speed higher than the reference speed. The aircraft landed too far down the runway, about 700 metres past the runway 28 threshold (runway 28 is 1,600 metres long). After touchdown, directional control was lost. The airplane veered off runway to the left and while contacting a drainage ditch, the undercarriage were torn off and the aircraft came to rest 20 metres further. All 17 occupants were evacuated, among them nine were injured. The aircraft was damaged beyond repair.

March 30, 2007 2 Fatalities

Airlink Papua New Guinea

Kandrian West New Britain

The aircraft was refueled with 640 litres (L) of Jet-A1 (AVTUR) in preparation for an early morning departure to Hoskins, New Britain, on 30 March. On 30 March, the crew lodged a flight plan, which stated that the total fuel on board was 2,100 pounds (lbs) (1,208 L). The first sector of the planned route was from Port Moresby to Hoskins. The pilot-in-command (PIC) obtained an area forecast for the flight, which indicated that there were areas of rain and scattered cloud from 1500-5000 feet (ft), with deteriorating conditions forecast for the period between 0400-0800 hours (hrs); for their arrival at Hoskins. The forecast required 30 minutes holding fuel in addition to the flight and statutory fuel requirements. These conditions were normal for their destination at this time of the year.The aircraft departed Port Moresby at 0402, as flight number ND304 for Hoskins. It initially climbed to the planned Flight Level (FL) 140 (14,000 ft), which was 300 ft above the lowest safe altitude (LSA) on the initial RNC track between Port Moresby and Girua, an Instrument Flight Rules (IFR) reporting point on the north coast of the PNG mainland. The LSA for the sector between Girua and the en-route reporting point Maran was 3,300 ft, and the PIC had planned to cruise at 9,000 ft. The sector between Maran and Hoskins was planned at 9,000 ft, with a LSA of 8,300 ft. The purpose of the flight was to transport newspapers and general freight to Hoskins and Rabaul. Flight Information Area (FIA) communications with Nadzab Flight Service used High Frequency (HF) radio, and a Very High Frequency (127.1 MHz) repeater transceiver located near the township of Popondetta. This service was usually monitored by Nadzab Flight Service during their normal hours of operation, for aircraft operating on the Girua to Hoskins track. One of the functions of the Nadzab Flight Service Unit was to record all transmissions received via the Girua repeater site. The crew made a position report, intercepted by Port Moresby Flight Service, advising that they were overhead Maran at 0506, cruising at FL 110 (11,000 ft), and gave an estimated time of arrival (ETA) Hoskins at 0540. That was 2,000 ft higher than the planned level. The position report was received by Port Moresby Flight Service, because Nadzab Flight Service had not commenced operations. It subsequently commenced operations for the day at 0540. Because Nadzab was responsible for the airspace in which ALU was operating, Port Moresby Flight Service advised Nadzab of ALU’s position report, once Nadzab opened. The Maran position report was the last recorded radio contact with the aircraft. No transmission declaring the intention to descend below FL110 was heard from the crew of ALU. No MAYDAY transmission was reported by ATS or other aircrew. When the crew of ALU failed to report their arrival at Hoskins, a search was commenced of the Hoskins aerodrome. At 0650 a DISTRESFA Search and Rescue Phase (SAR) was declared indicating the degree of apprehension held for the safety of the aircraft and its occupants. Later that morning verbal reports were received from a coastal logging company in an area east of Kandrian, that an aircraft had crashed. The wreckage of ALU was found 27 km east of Kandrian, at an elevation of 780 ft above sea level. Both crew members had not survived the impact. The wreckage was located at position 06° 11' 39.8'' S, 149° 52' 58.9'' E, and was dispersed along a 500 m wreckage trail after colliding with numerous trees and impacting the terrain. The investigation estimated the time of the accident to be about 0523.

August 4, 2006 1 Fatalities

AirNow

Pownal Vermont

The airport's instrument approach procedures included a very high frequency, omnidirectional range (VOR) approach, and a global positioning system (GPS) approach that was not an overlay. The VOR approach procedure included an inbound course to the VOR, and after passage, a descent along the same course to a missed approach point. The missed approach point was defined as 6 nautical miles beyond the VOR, as well as by timing. The pilot twice attempted the VOR approach in instrument meteorological conditions. He flew the first approach to the missed approach point, initiated a missed approach, contacted the controller, and requested a second VOR approach. He then received vectors to rejoin the approach course inbound to the VOR. The airplane subsequently passed over the VOR, on course, about 100 feet above the minimum altitude. However, instead of descending as described in the procedure, the airplane maintained that altitude until reaching the airport, then began a descent. The airplane continued to travel outbound along the same approach course until it impacted rising terrain about 6.5 miles beyond the airport. There was no dedicated distance measuring equipment (DME) onboard the airplane. Instead, distance was determined by the use of an instrument flight rules (IFR)-approved GPS unit. Due to the non-storage capability of the unit, historical waypoint selection could not be determined. The pilot could have selected the airport as a "direct to" waypoint, or, if he had entered flight plan waypoints, the unit would have sequenced from the VOR to the airport during the first approach. In either case, unless the pilot reprogrammed the unit, the last waypoint entered would have remained at the airport, rather than the VOR. The pilot then most likely mistook the airport position for the VOR position, and displaced the beginning of the descent by 6 nautical miles. Also noted, was that once the airplane passed over the VOR en route to the airport, the HSI would have indicated a change of "to" to "from". There were no medical anomalies noted with the pilot and no mechanical anomalies noted with the airplane.

Page 1 of 8